Andrew,
I'm not sure how this can happen. We do everything according to the rules by specifying a filename when we pump the file to the client. This is set to the same name as the original filename when uploaded. Aparently browsers can disregard this header and make their own name. There is a chance the new download method will solve all issues.
Peter