While the main reason for this behavior is not quite clear yet, I can suggest a small workaround to bind the vmkX to only vmotion so that other vmk is not used.
In ESX-configuration-software advanced settings-Migrate-migrate.vmknic. set this value to vmk1 or any vmkX as you wish to set. This way the vmkX will not be used for management purpose.