Sorry, but your problem does not imply a bug in PHP itself.  For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system is not the
appropriate forum for asking support questions.  Due to the volume
of reports we can not explain in detail here why your report is not
a bug.  The support channels will be able to provide an explanation
for you.

Thank you for your interest in PHP.

That's expected, arrays have always worked like that.

Following will give a different result. Just because reference is copying after assignment.

PHP manual says the assignment operation copies by value for arrays.

<?php
$arr1 = array(1, 2);
$arr2 = $arr1;
$var = &$arr1[0];

$var = 10;
print_r($arr1);
print_r($arr2);
?>

Yes, the array itself is copied by value, but not the array content, as you discovered.

$a = array();
$b = $a; 
$b[] = 2; var_dump(count($a)); // int(0)

The example you gave behaves expectedly and actually denotes the bug is valid. I would request you to carefully go through the two code snippets I gave.

Even when you copy a value by reference the array, the copy is not actually made and instead the refcount is increased of the array. PHP will defer the actual copy until any one of the array is actually modified. 

Now when you copy the reference to the any array item, and modify using that reference, a new copy is created and values updated. But if you keep the reference of the item in a variable before array copying, modifying this variable will not force PHP to create the actual copy of the array.

Incorrect behavior at the best.

Again, those are expected results, when you copy an array, its  elements that are references will be copied as references. It has always been like that.

Ok.
But it is not obvious from the documentation. A cautionary statement should be included in there.

Moreover, variables, which are references, when copied are not copied as reference and instead a true copy is made. Array elements should not be treated differently.