Node deletion can leave unrelated entries in the scheduler table

scheduler_nodeapi does nothing if current user has not the 'schedule (un)publishing of nodes' access right. It is wise for load, submit, insert and update operations but not for the delete operation.

If the current user can delete a node but has not the 'schedule (un)publishing of nodes' access right and there are still scheduled (un)publish task on this node, the scheduler table will still contains entries with an incorrect nid.

I think it does also apply to the 5.x branch.