Yes I did. Apparently I do not interpret it the same way that you do. I took the following to mean that you did not need to enable AWE to use the AWE API's on 64 Bit. We do not do this with our 64 bit servers. We were able to prevent the working set from being trimmed by merely locking pages in memory (in addition to setting Min/Max Memory properly).
For 64bit systems, the virtual address space limitation is not an issue. However, if an application wants to "lock its memory" or avoid its working set from being trimmed, then it can achieve this by using the AWE APIs. Again, in order to use these APIs, you must have the 'lock pages in memory' privilege set. This is why for 64bit systems, you don't need to set the 'awe enabled' option to 1 (it is actually ignored on 64bit systems).