Closing a WebSocketBehavior and opening it again

When a service derived from WebSocketBehavior is closed the base class does not set _websocket to null. Then when a client tries to reconnect it fails because the base class thinks the session is already started.
I have this workaround in place in the derived class:

    protected override void OnClose(CloseEventArgs e)
        {
        // ...
        var base_websocket = typeof(MyService).BaseType
                .GetField("_websocket", BindingFlags.Instance | BindingFlags.NonPublic);
        if (base_websocket != null)
            base_websocket.SetValue(this, null);
        }

Locate WebSocketBehavior and its OnClose lifecycle, then inspect how _websocket is initialized and checked when a client reconnects. Confirm the close-and-reopen behavior with an existing test or reproduction if available, and verify that the derived-class reflection workaround is no longer needed.