That’s a good point. You and @NigelG have prompted me to reconsider the approach I had planned to implement.
A recent hurdle I encountered was dealing with orphaned images/files that are uploaded as part of the form - be they user profile images or attachments, or whatever - as they consume valuable storage space. Things are pretty straightforward when the app logic is responding to explicit user actions - i.e. user clicks cancel, then delete files - but the possibility of abandoned pages or connection loss complicates things a bit.
I came up with this approach to deal with orphaned files based on some input from @JohnMark. I think it should work with or without auto-binding. Any input in that regard would also be appreciated.