#19398callUserFunction and getUserObj uses different object pools
Description
Both ways of instantiating an object has the possibility to instantitate the object as (pseudo) singleton by prefixing the classname with &.
But they use different object pools, namely:
$GLOBALS[‘T3_VAR’][‘callUserFunction’] and $GLOBALS[‘T3_VAR’][‘getUserObj’]
This prohibits the use of references to objects across different hooks/callbacks
(issue imported from #M9458)