Resolution:
The temp destination behavior has been changed in EMS 4.4.x to  comply with JMS spec.

When an application using EMS 4.4.x client library creates a temp destination in EMS 4.4.x Server, if the temp destinations have no receiver or pending messages, it will exist until the applications explicitly delete the temp destination or until the connection is closed. Since the behavior of temp destinations are not like dynamic destinations , so that the applications have to maintain them better (delete them properly or reuse them) than dynamic destinations.

When both the EMS clients and EMS server upgrade from lower version to 4.4.x, it's possible to see temporary destinations are not removed in EMS 4.4.x server which is not seen in earlier EMS version. The application has to be changed to delete temporary destinations or reuse them properly.

Why temporary destinations are not removed in EMS server 4.4.x even there is no receiver and pending messages?