Message 189117 - Python tracker

Basically the logic is this:  When the class goes away, it _always_ calls remove_subclass().  Now, this may be before or after the weakref has been clear so that it will either find itself in a weakref, or a clear weakref.

In case this logic is flawed, we know that when remove_subclass() is called, exactly one child is removed.  Whether it is us, or some previous class, is irrelevant.