XML entity expansion affecting connection pool sustainability

Assuming XML 1.0 feature compliance, investigating how XML external entity expansion influences connection pool sustainability in standard server deployments. The goal is to determine whether uncontrolled entity growth can trigger pool exhaustion independent of application-level resource management.

Key uncertainty involves the threshold at which entity expansion consumes sufficient memory or I/O to starve connection pool acquisition routines, particularly when parser configuration defaults differ across XML processing libraries. The interaction between DTD feature flags, schema validation depth, and pool recycle timing remains unspecified in typical deployment guides.

Does disabling external entity resolution eliminate pool exhaustion vectors during sustained XML ingestion? How does schema validation strictness affect connection pool block duration under concurrent document parsing? Is there a measurable correlation between XInclude inclusion depth and connection pool starvation in multi-threaded contexts?