When deleting zones it is counter intuitive that there may still be an enforce task for that zone

There are issues when deleting a zone.
First there is the generic problem (as with the add zone), that the instruction is asynchronous and the return of the command does not mean the zone has been deleted yet.

However the most intuitive issue is that when adding and then immediately deleting the zone, there will still be an enforce tasks queued for that zone.
This will happen on a number of scenarios, and has mainly to do with the fact that the enforce task is actually not for /that/ zone, but for any zone that needs updating. Since the naming is incorrect and gives too little information (which zones actually need updating), the task cannot be deleted.

Yet it also makes testing and expected behavior more difficult, since the task will remain even if it would be possible to remove it (when there are no other tasks for example).