The executor connection pool host timeout is racy with respect to other code that's unlocked the parent mutex to allow for callback execution.

While effort was spent to protect against background threads with active requests and those participating in refresh, after those tasks have been executed we race with callbacks in how quickly they can return. When we lose that race, we destroy the specific pool out from under those callbacks.