I reproduced the bug in 32-bit Excel 2007, 2010, and 2013. I then reported it to the person at Microsoft who maintains the bug tracker.
My guess is that this will receive a "won't fix" type of response, but perhaps they will get to it in the next version of Excel.