I discovered today that if both displays are set to the same refresh rate then the bug does not occur. This is an acceptable workaround for us, however, I still consider this a bug that Apple needs to fix.