Actually, Apache can access the files directly. That's how it serves the actual content.
What I was referring to was the symlinks themselves. There are options you can put into httpd.conf or .htaccess files to permit Apache to follow symlinks; it's generally not recommended though, as a bad guy could set up a symlink to something secret like /etc/passwd and Apache would blindly follow it.
I'm guessing you're trying to make domains visible that don't have DNS propogation completed yet...?
There should be a way to do it, especially as you can add Perl into the httpd.conf file if needed (although it can get a bit ugly if you're not careful) to look up the corresponding "real" path to the site indicated by the symlink... I don't have enough time in my schedule to tackle it myself directly though; sorry.