However, what I did discover was that once you push a new Task into the worker instance a "memory leak" occurs. The worker just keeps on creating objects even when there is no acitivity. This can be seen on a memory monitor.
I think you need to return true instead of false (@return <code>true</code> if the task need to be removed after execute).

