_replication database pruning

[Steven Ringo]

I notice the _replication database fills up with entries as one-off 
replications take place. In the case of many replications being fired 
off (e.g. filtered per-user) the database may end up getting large.

Like log file rotation, etc. is there a way to automatically prune or do 
something to keep it cleaned?

Thanks,

Steve