ExclusiveConnectionPool's Clear() appears to simply abandons all existing connections without closing them.

If Clear becomes a blocking operation then we're going to need a ClearAsync version also.

Closing the connections in the background is dangerous because it creates a possible race conditions where connections are opened faster than they are closed leading to resource exhaustion.