"dangling refs" in object pools create too many refs

In !1297 (merged) we introduced a mechanism to prevent accidental deletion of objects from object pools. The idea is that if an object becomes "dangling", meaning there is no ref pointing to it, we just add a new ref to un-dangle it. It turns out this creates too many refs.