When one ManagedConnection is destroyed the pool's ServerLocator gets destroyed as well

An issue was discovered in which when destroy() was called on a managed connection, stop() was called on the managed connection factory which stopped the ServerLocator and subsequently all sessions all the managed connections associated with that factory. The root cause of this issue has now been resolved.