Are you still having this problem?
A ControlConnectionThread lives on the client side of a Remoting/JBossMessaging connection, and it monitors the bisocket control thread for requests from the server to create sockets. One is created per connection, and, if you have pinging turned on for the control connection (which isn't the default in most or all versions of JBossMessaging), a new one will be created if the pinging times out, in which case the old one will be shut down. Are you creating a lot of JMS connections at once, or accidentally leaving them open?
As you said in a particular negative scenario one of the JMS connection was opened and never closed. This leaded to increase in the thread leakage which ultimately leaded to increase in thread count in JBOSS and particular Java application where we had spawned these connections. We had fixed this issue two weeks later by running the trail version of JProfiler in remote mode. We found a thread count increase rapidly in the Jprofiler GUI and we caught the place where the thread leakage was happening
Thanks and Regards,