RemoteCacheProducer injects an (optional?) default RemoteCacheManager, which is created with a custom bean registered by InfinispanExtensionRemote.createDefaultRemoteCacheManagerBean().

In the CDI remote tests, however, the default RemoteCacheManager is not used, so it's not created. Instead, Weld creates a proxy RemoteCacheManager, and since RemoteCacheManager is a class, its default constructor is invoked, connecting to the server and starting the async thread pool. But since it's not a proper bean, only a proxy, Weld never invokes stop() and leaks the thread.