I haven't upgraded iTunes yet to 7.6, but witnessed this behaviour on a friend's machine.
When I looked into trying to figure it out, my first thought was that it might be a line terminator issue, which it appears not to be. I clicked and saved the same .m3u from eMusic in Safari (1), Firefox (2), and via curl (3) to see what I could discover.
First off, all three files have CRLF terminators, so that doesn't seem to be the issue.
% file 16079502*.m3u
16079502(1).m3u: ASCII English text, with CRLF line terminators
16079502(2).m3u: ASCII English text, with CRLF line terminators
16079502(3).m3u: ASCII English text, with CRLF line terminators
Next, I thought I'd compare the files using md5...
% md5 16079502*.m3u | column -t
MD5 (16079502(1).m3u) = b4d9b4bd44a0408796bf9a6b7597d65c
MD5 (16079502(2).m3u) = 3d096d8d1583f5508e836784e878c493
MD5 (16079502(3).m3u) = 2480bcf971f2a2c1170c7654cce77b5c
...which ended up showing me that every .m3u downloaded from eMusic is different anyhow, because they create a unique URL each time you make the download request. I proved this to myself by running the same curl command repeatedly and watching the sum change every time, and then running it and just plain looking at the URL change each time. So, that became and invalid test.
Moving on with Taxinator's approach, I checked out the metadata for each of the files.
% mdls 16079502*.m3u | grep FST
kMDItemFSTypeCode = 0
kMDItemFSTypeCode = 1297101653
kMDItemFSTypeCode = 0
Yep, Firefox's file is the only one that has a non-zero value in the metadata.
Why would this be happening, and to be really blunt, why would simply reading and writing the same text file via Applescript (the file un fcker script mentioned all over the net) actually fix this?
How does this meta data get set, and reset?
I find it difficult to believe that this is an issue caused by Firefox, since the symptom arose with an update to iTunes, not Firefox. Needless to say, Firefox's behaviour had not changed at that moment.
So, did iTunes suddenly become incredibly strict about metadata where it had not been before?
Anyone fine a more reasonable fix for this issue other than to force using Quicktime or recreating every .m3u file downloaded via Firefox?