Cache managers failing to start do not stop global components

If one of the global components fails to start, GlobalComponentRegistry.start() removes the volatile components, but it doesn't call stop() on those components.

The most likely reason for a global component start failure is a timeout in JGroupsTransport.waitForInitialNodes(). After such a timeout, the transport isn't stopped, so the channel's sockets and threads are only freed after a few GC cycles (via finalization).