This is usually not problematic since the reaper should kill it but if the reaper timeout is high this could cause other operations waiting on conflicting locks to wait on lock acquisition.

See this comment for more details. 

Either mongos can retry and make more of a best effort to abort transactions at shutdown or ClusterServerParameterRefresher can do it's work outside of a transaction as suggested.