Within a day of making a post on SQL rights, I was contacted by Chris Gideon of our support arm and he quickly pointed out some big reasons why you do NOT want to remove dbcreator, even after the databases are created. I will be modifying my SQL Rights post in addition to this new post to reflect this guidance. Thanks very much for this information Chris!!
823282 You receive an SQL access error message when you change the configuration database administrator account in SharePoint Portal Server 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;823282
823287 You receive a "Cannot connect to the configuration database" error message when you connect to your Windows SharePoint Services Web site
http://support.microsoft.com/default.aspx?scid=kb;EN-US;823287
828815 You receive a "Database <Database_Name> already exists" error message when you manage your Windows SharePoint Services content database
http://support.microsoft.com/default.aspx?scid=kb;EN-US;828815
841216 "0x80040E14" or "HTTP 500" error message when you connect to your Windows SharePoint Services Web site after you install a Windows SharePoint Services service pack or a security update
http://support.microsoft.com/default.aspx?scid=kb;EN-US;841216
889646 "Error 18456" error message when you specify configuration database settings on the Set Configuration Database Server page of SharePoint Central Administration
http://support.microsoft.com/default.aspx?scid=kb;EN-US;889646
896148 You receive error messages when you try to use the Stsadm.exe command-line tool to perform certain administrative operations in Windows SharePoint Services
http://support.microsoft.com/default.aspx?scid=kb;EN-US;896148
906950 A backup operation is not successful when you use the SharePoint Portal Server Data Backup and Restore program to back up portal site content in SharePoint Portal Server 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;906950