I have installed the 4.0 code dated 12-8-2004 and am experiencing this problem.  Just went to the demo site and (to my suprise!) discovered it also was doing this.  I could swear that last Wed or Thursday all was well with the demo site.  Do I have the most current build with this fix -- or -- are you still testing the fix and have not released it yet!