May be a result of the index-based selection (which I dislike immensely but would tolerate if it worked)

The selected object should not change as a result of sorting, even though the selected index does change. Currently listeners on the Selection model's selectedObject are fired twice. Once indicating a null selection, then again in an attempt to restore the selection (which is often incorrect after unsorting)

See also RT-36352