We have observed that the kCurrentScope variable sometimes retains a reference to a destroyed ImplScope in dynamic builds. A fix was identified in the code review for SERVER-46296, but that work is blocked on startup performance. This ticket exists to split the fix out from the SERVER-46296 work so we can commit just the fix for the handlign of kCurrentScope.