Personal opinon: At this point, we tend to use Forms for complex UI apps with lots of validation and pretty intense usage.
If you can meet the business needs easily in a pure-web tool like ApEx (or any of hundreds of others), I wouldn't use forms.
So you'll probably need to assume that many of those Forms users are going to be keeping their connections pretty active.
And complex Forms use a lot of memory. We're running the app server on 34-bit Windows (not my choice) and running into memory limits with about 50 active connections.
Forms is pretty good on concurrency, so with reasonable coding you're not going to hit any major database limits. And app server processing and IO won't be your constraint. It's really just a matter of how many active users you're dealing with at one time, what their memory footprint is, and how big or how many app servers you're willing to deal with.
(Background: Forms Developer since version 2.3 (with a bit of 2.0), still using it for some projects and a lot of legacy)