I did consider doing this, but went with the way I've done it because:

* the `JobStoreService` is now starting to look a lot like a fairly standard persistence layer with `save`, `delete` etc
* the "algorithm" for deleting is more business logic type stuff that doesn't belong in the above.

Having said that, maybe you could have a `delete(Closure)` method, but I can't see much benefit in doing that...