`pipe_notify()` requires certain sequencing of cleanup actions

`pipe_notify()` currently takes a socket and registers pipe events against the `conditionVariable` supplied. This means that the 'cv' has to remain available (and cannot be garbage collected before) the socket is closed, or the pipe notification cancelled.

It is currently assumed that expert users of this function would ensure that this happens, but there is no failsafe mechanism.