Good question. The intention was to not keep objects (the initializer/uninitializer) alive on long-lived threads. However, this not much of an issue with functions and weakrefs to bound methods are ephemeral. The only possible issue this could solve is with callable classes, but then you'd probably want to keep the uninitializer alive so it can actually be called.

I'll put in a patch to remove this. It does not make any sense.