We have an aggressive invariant here. This means that we crash the server whenever we attempt to replace an OperationContext instead of explicitly destroying and then recreating. We can keep that invariant in test environments. In production, I believe we should interrupt the previous OperationContext to produce an AssertionError. We should probably also log and emit an exception at the call site to make sure we don't end up in an unsatisfiable wait.