Description:
------------
Hello,

In my opinion, the Garbage collector of PHP have a strange behavoir on order calling __destruct methods. So the documentation say that GB call __destruct of an instance of object after all references destroyed.

But this is not true if it have a reference on a static (global) scope. But for me a reference is one that is in a global scope or not.


I think this is a bug, and if this is not, can you explain to me why GB have this behavior ?

Test script:
---------------
http://pastebin.com/pTb1fqQK

Expected result:
----------------
Show C Destruct C Show B Destruct B Destruct A

Actual result:
--------------
Show C Destruct C Destruct A Show B Destruct B