@asmecher - thoughts on this one? The bug that you mentioned in the thread reference seemingly is resolved for 3.3.0-21 - might something else be causing this?
-Roger