NOT12 — Semantics of Disconnected exception

Summary: It would be nice if the spec explicitly stated what happens when a pull
supplier or push consumer raises the Disconnected exception. One way to
look at it is that when the client raises Disconnected it no longer
wants to send or receive any events and it"s basically disconnected
(i.e. the same as if the disconnect_xx_yy operation was invoked).

I believe this is an issue because the disconnect_xx_yy operation
controls the lifecycle of the proxy. If the above interpretation is
valid, the proxy will be destroyed when the client raises Disconnected.
Alternatively, the proxy could just change its state back to not
connected (the same state as when the proxy was just created by an admin
object).

resolved, see below