Not sure abut this one. First, the boolean passed to the method is indicating whether the thread running the task may be interrupted while running or not (`cancel(false)` doesn't really mean cancelling only if not started; some tasks understand the concept of being cancelled and will stop processing when this signal is received). Currently we don't support that thread interruption, so the boolean is meaningless really. But I'd like to leave the option open to implement such a feature, where we are able to asynchronously run tasks that were not meant to be asynchronous (an thus have no concept of "stopping"), but at the same time being able to forcefully cancel them. this might require some thought and prototyping (and might not even be possible with Seam 2), and since it wasn't really an option in the previous setup, I didn't bother going into it.