Maybe the object itself keeps itself alive? Maybe it has child objects that keep the parent alive too?

My guess is that your object SomeClass will never get released until global destruction.

My advice is to rip out code from SomeClass until it starts getting released at the appropriate time, and then slowly putting the code (and the SomeClass-internal calls to the code) back in until the leak reappears.