It's a creepy but known issue. I believe this will be addressed in patch 2.1.2.