Description:
------------
If you use singleton classes, it is often handy to have one global instance of your class and manipulate this instance using static functions. Then it can also be handy to call such a static function for cleanup purposes inside the destructor. However, if the object is cleaned up using unset(), the static functions lose access to the global instance before the destructor is finished. If the instance just runs out of scope, it works normally however.

Btw, this bug seems somewhat similar to Bug #29685 in which it also appears the destructor is called too late with a singleton pattern, with the exception that this code does not have a private instance and simply uses a global instance.

Reproduce code:
---------------
class Test
{
        public function __construct() { $this->a = "test"; }
        public function __destruct() { self::printA(); }

        static public function printA() { global $test; echo "$test->a\n"; }

        private $a;
}

$test = new Test;
unset($test);

Expected result:
----------------
It should print: "test".

Actual result:
--------------
It prints nothing.