destroyed. These are BisocketServerInvoker$ControlConnectionThreads. They run on the client and handle "create connection" requests from the server coming in on the control connection. When org.jboss.remoting.Client.addListener() is called, a BisocketServerInvoker is created on the client side, and a BisocketServerInvoker$ControlConnectionThread is created. When Client.removeListener() is called, the BisocketServerInvoker$ControlConnectionThread is shut down. But in this case (and it happened in one other support case), the number of BisocketServerInvoker$ControlConnectionThreads just keeps growing. I created a jboss-remoting.jar with extra logging which shows that JBossMessaging doesn't seem to be calling Client.removeListener() before it calls Client.disconnect().