If your pretty savvy you can also switch to mod_log_sql and store them all in a database. Saving your server ALOT of work but making your job a little more interesting pulling the data back out and running it through a log analysis application.
I am using it on a server now and its great to be able to add a vhost with no logging info setup in the httpd.conf for the host and it automatically start logging all the access / error logs to the database. They also include a small perl script to pull the data back out for you to use with Urchin, AWStats or Webalizer
Here's my 'first thought that springs to mind approach'...
If you want your log archiving tool (I use newsyslog) to rotate all your apache logs, you'd probably want to write a quick tool in Perl or C to parse the httpd.conf file and then append whatever logs it finds to /etc/newsyslog.conf.
Edit: Thought 2 -- or opendir/readdir your log directory and throw anything that looks like a log file to the newsyslog.conf.