Description:
------------
Please let me know if I have misunderstood the whole idea behind the reflections.

I use callbacks in my code a lot, and they are good when I use 
call_user_func_array() along with array($object, $method) as the argument.

This makes abstraction and normalizing handler classes very easily.

But I found this code pattern difficult to port to the reflections, as long as 
there is nowhere I can pass the method along with the reference of that 
particular object in the reflection class.

Imagined scenario as follow,
```
$object = new MyHandler($initialize_options);

$callback = new ReflectionMethod($object, 'handleResult');

$net->request($parameters, $callback);
```

Expected result:
----------------
ReflectionMethod::invoke() and ReflectionMethod::invokeArgs() should have their 
first parameter remains optional, but calls a non-static method even when NULL is 
specified in case an object instance is provided in 
ReflectionMethod::__construct().

Actual result:
--------------
ReflectionMethod::invokeArgs() takes the first parameter as the object reference, 
static method is assumed if the first parameter is omitted (NULL).