http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=626299&SiteID=1

Apparently using replication monitor causes this problem. I'm going to reiniatalize our replication tonight, not use replicaton monitor for a week and see if this is really the problem.

James