I respectfully disagree. Why is it then that my Samsung has no issues while using Merlins firmware based on the older drivers, yet has issues with the newer releases with new drivers? And why is it that in this very same Asus forum other people with HTC phones are reporting the very same issue? D-Link managed to get their firmware right with their last update as well... Seems like enough evidence pointing to it being an Asus issue.
Actually, there is a good chance that this is a problem with Broadcom, since this is the common point (AFAIK) between all affected routers (since the issue affected Asus, DLink and also Linksys at least). Since the issue seems to be specific to AES encryption, there's a chance that it's something in Broadcom's crypto library, not in the wireless driver itself (otherwise, I would expect to see TKIP affected as well).
There's still a chance the issue can be with Samsung too. Sometimes, a manufacturer will push the specifications beyond what's official. Implementing a new feature can end up breaking clients that do not properly follow that specification. Take a look at the XBox360 issue, for example. Asus's fix was to disable a wireless feature (LDPC), which was possibly not properly implemented by Microsoft, which is why it only affected the XBox 360.
Without knowing the technical details of the fix DLink implemented, it's hard to say beyond speculations.