Comment 2 for bug 1400326

Update: depletion cannot cause the lock since in this case a new connection is created.
However, this new connection is returned to the pool afterwards.
Consequently there are +1 connection.
While there is a depletion check in the poll on the connection aquire, there is no such check on the release.

All this results in indefinite lock on connection release, if connection excess is high enough.