Java heap retention due huge numbers of org.jboss.ejb.client.EJBClientContext

Issue

• Poor GC performance.
• GC full collections are not able to reclaim old generation space.
• Heap analysis shows 1+ million org.jboss.ejb.client.EJBClientContext
• log file showing this error:

javax.naming.NamingException: No provider URL configured for connection
  at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:196)
  at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:196)
  at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:171)
  at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:171)
  at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:146)
  at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:146)
  at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:122)
  at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:122)
  at org.jboss.as.naming.InitialContext.init(InitialContext.java:107)
  at org.jboss.as.naming.InitialContext.init(InitialContext.java:107)
  at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154)