"as of the latest ptr build for patch 4.0.6, it looks like this is not being``fixed"", but is intentional."
It could just be from the datamining of what has already been shown to be true through the plethora of comments here.