Yes. You have to go back to the reason for ConnectionReleaseMode being added to understand (hint look above at summary). In fact we discussed both of these and opted for ConnectionReleaseMode over changing the "acquisition mode" based on just this argument and with the belief that getting the connection over and over from the DataSource would be not a big performance hit. But in the interim we have actually seen people complain about the performance of releasing/reacquiring connections over and over from the DataSource. Plus I think we need to be honest about the real impact of getting a connection and not using it. Aside from micro-benchmarks, what does that really affect?

Bottom line is that we need to make sure the Connection does not leak across boundaries. So we need one of these 2 to handle the cases listed above. I am simply suggesting adding the alternative for those that don't want the multiple release/acquire cycles.