Finder gets stuck when reading contents of large folders on a SMB-share

Question

Hai thar, everyone. Recently I've found a sad bug in the world's most advanced OS. I wonder why it was left almost unnoticed as I was unable to find out some info on it so I created this topic in hope to turn attention to this issue when no solution is available right now by far. In short, bug consists in Finder's misbehaviour when it reads contents of big folders on a mounted SMB-shares like stated in the title. Number of files - somewhat around 11-12 thousands/folder. What't interesting, when one goes to the shared folder which contains not much files (below critical limit) - everything's just fine. When one opens a "bomb"-folder, Finder does nothing. It won't display folder's contents and moreover, it won't display contents of other folders on the share anymore, however, it's still able to show up contents of those folders you have visited just before opening "bomb"-folder. Probably it simply has  the contents of visited folders cached somewhere. The second consequence, connection to the SMB-share seems to degrade. Speed drops to miserable numbers and case you open some big file from the share theres a chance that it'll be loaded slowly. It's not that hot idea in fact, to load network by watching videos directly from the SMB-server =) but if you do open a movie, playback will be jerky as **** while it was perfect just before you poked the "bomb" and current traffic is very little - a few kbps/~100bps (according to Activity Monitor). As stated before, stuck Finder seemingly affects overall connection to the SMB-server in some strange manner. FS notifications get broken too, on the share.
In general Finder proceeds functioning. It has no problems with local FS/other kinds of remote FS, but SMB. It looks like theres a stuck thread serving requests to for the file objects on the SMB-share which actually gets stuck or does extremelly slowly.
The workaround is pretty simple and straight forward - you have to restructurize your "bomb"-folders by splitting them into several subfolders or such. Simply get rid of that huge heap of files stored in a single folder, fragment them and keep their number below 10k/folder. However, this is not a fix. It's only workaround. Fix should follow, as this issue is not only a "little inconvenience" but also a software flaw.
This bug affects at least OS X 10.7.5 (11G63). Something similar was seen also on OS X 10.6.6
WBR
PS: sorry for my broken English.

Answer 1

Reporting the same problem.
1. Have Windows 7 MediaCenter with file sharing set up properly (LM+NTLM Authentication allowed and 128-bit encryption disabled in security policies).
2. Test folder ("C:\income") and all the subfolders' owner is 'Guest', full access is granted for everyone.
3. Connecting to MediaCenter from MacBook with Finder by pressing Cmd+K and typing smb://ip-addr/income
4. Finder connects successfully, but some sub-folders and files are not being listed.
Workaround:
5. You can open a not-listed folder directly by pressing Cmd+K and typing smb://ip-addr/income/some-invisible-folder
6. Voila! You're inside invisible folder.
In the meantime, i can see all the sub-folders on a Windows XP client machine, so i can make a conclusion that all of these 'invisible' sub-folders are actually accessible by Finder, but in some reason are just not being listed on Mac.