We've been in the same position. We've been able to use Windows Scripting Host and VBScript to create some reports that help.
1) Service accounts. As you know, the password for a service account is stored separately. We've been able to create a script that uses ADSI to connect to the domain and enumerate all computer objects with a server OS. Then for each computer, we use WMI calls to enumerate any services where StartName <> LocalSystem. This gives us a nice report of all services that start with a domain account.
2) Scheduled Tasks. We have a lot of scheduled tasks on servers that run under a variety of domain service accounts. Creating a script to enumerate these is tricky, and requires a little-known Resource Kit tool called JT.EXE. But the end result is that we get a report of all scheduled tasks on all servers...their status and their account credentials.
Actually CHANGING these stored passwords is still a laborious manual task, but at least we have a list to work from, so we don't miss anything.