Thanks for calling our attention to this. We've duplicated the problem here and we're in the process of tracking it down.