If they re-appear automaticly, they could be started by an SQL Agent job or perhaps by an application (like a monitoring application). You need to find out the process that starts the trace(s).
In SQL2000 there is no default-trace like there is in SQL2005+, so the running traces are not required by SQL itself.
** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **