javax.naming.InitialContext#close method rarely hung on standalone JMS client

Issue

javax.naming.InitialContext#close method rarely hung on standalone JMS client. Thread dump during the hang-up shows as the following stack:

"main" #1 prio=5 os_prio=0 tid=0x00007faa8c00c800 nid=0x4a4a in Object.wait() [0x00007faa94212000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:189)
        - locked <0x00000000e0b39760> (a java.lang.Object)
        at org.jboss.naming.remote.client.EndpointCache.release(EndpointCache.java:79)
        at org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.close(EndpointCache.java:194)
        at org.jboss.naming.remote.client.InitialContextFactory$1.close(InitialContextFactory.java:232)
        at org.jboss.naming.remote.client.RemoteContext.close(RemoteContext.java:290)
        at javax.naming.InitialContext.close(InitialContext.java:556)