Hey Gang -
It seems that it's flyertalk to the rescue.
This was never intentional in our programming.
We had been made aware that this issue was happening but hadn't quite nailed down the reason or the fix.
After reading your posts today, we have already implemented a fix so you should no longer be having this issue.
Thanks,
SWAVictor