Cause:
http://news.php.net/article.php?group=php.zend-engine.cvs&article=1432

I wonder if we really should break BC here...

Well from the text of that item it would suggest that doing:

return new object(); 

is fine, but:

return (new object());

is not fine, that's how it would seem to me as an end user.

 PEAR is ridled with returns like the one I list (Although IMHO it should have only one return and assign return values to a variable then return at the end, but that's another story).

I have the same error, it seems like it comes from a function that must return a reference, but objects are already references.

this doesn't work, but worked before beta1, I tried PEAR before beta1 and it uses lots of this :

function &myFunc()
{
    return new MyClass();
}

This works fine :

function myFunc()
{
    return new MyClass();
}

I don't understand why it comes from return (new Class()); cause it doesn't work.

What is the meaning of returning result of new by reference?

I think it is the same problem as here : http://bugs.php.net/bug.php?id=24687

As zeev said, in the current zend2 you can't connect to a returned value.

But it is really needed to unreference returned value, and you can do it in most object oriented languages.

Here, we break a compatibilty with PEAR, Horde (and other projects I guess). For now, I am waiting for a new version of PEAR, and then Horde.

Same as bug #24687 (add your comments there, if any)