We just came across this issue in 1.11.
tested in 1.9.2, still an issue
confirming for 1.9-pre4
confirming for 1.9 pre 2
confirming for 16w07b
since this was re-opened again: confirming that this is still an issue in 16w02a
update: same for 16w03a (and all the versions between the initial reported once and this one)
At the chance of "necroing" this: It was always an issue and still is (1.11.2 for sure, snapshots extremely likely but would need to test)