You can enable logging on the session related classes, and you can also turn on resource diagnostics to track down unreleased sessions.
1. Enable resource logging in dfc.properties
add the key, dfc.resources.diagnostics.enabled=true
2. Enable logging in log4j.properties for session and resource related events
log4j.logger.com.documentum.fc.client.impl=DEBUG,SESS_LEAK_DETECT
log4j.logger.com.documentum.fc.client.DfSessionLeakChecker=ERROR,SESS_LEAK_DETECT
log4j.appender.SESS_LEAK_DETECT=org.apache.log4j.RollingFileAppender
log4j.appender.SESS_LEAK_DETECT.File=C\:/Documentum/logs/sessLeakDetector.log
log4j.appender.SESS_LEAK_DETECT.MaxFileSize=100MB
log4j.appender.SESS_LEAK_DETECT.MaxBackupIndex=5
log4j.appender.SESS_LEAK_DETECT.layout=org.apache.log4j.PatternLayout
log4j.appender.SESS_LEAK_DETECT.layout.ConversionPattern=%d{ABSOLUTE} %5p [%t] %c - %m%n