The tasks on the waitinglist are not present in the taskslist,
so let's not incorrectly attempt removal in this case.
We didn't check the return value here, and the disconnection event
won't even happen in the typical cases, so this has been unnoticed -
until the deletion actually did find a matching msgid (lucky!)
by a *different* task (of course) which triggered an assertion (crash).