...

This is not suitable for asynchronous methods.  

@Stefan and Patrice: Am i right here?

(Also see continues sending in IS advanced notes for better understanding)

New approaches / solution

Possible approach:

Analog to the container method, but the sending of information would be triggered  for example after each 5 method closure. (Ask if the size sending strategy is just that.)
To distinguish the method invocations done by the current thread from this done by other threads, each thread\runnable would get an ID(Remember thread pools and runnable reuse). 

Questions / Possible Problems

...