EnterpriseDB is layered atop Postgresql. As I understand it, EnterpriseDB uses Slony in at least one of their replication approaches. These files sound like they may be the Slony write history files, which are used to store a complete history of all changes to the database. Depending upon replication subscriber update frequency and history write rate, three days might be fine, but then again, it may not. All replication subscribers must be 'done' with a write history file before you can archive it.
Normally, whenever a complete backup is made, you would start with a fresh set of write history files.