Really depends on what you need to do, but per the below link it's not a recommended architecture. Isn't IT fun? :)
http://www.onjava.com/pub/a/onjava/2003/02/26/flash_remoting.html Use a Service-Oriented Architecture While you can directly access and invoke methods on servlets, JSPs, and EJBs with Flash Remoting, it does not mean that you should. It is important here to consider what Macromedia is doing today, what they are likely to do tomorrow, and where enterprise application development is going in general. In all of these areas, Service-Oriented Architectures feature heavily. A Service-Oriented Architecture describes an application designed to expose a set of loosely-coupled business services that may be accessed by a range of clients to assemble application functionality. Clients may be J2EE or .NET applications or Flash clients. This architecture makes the applications providing the services flexible and scalable. Enterprise application developers are rapidly adopting Service-Oriented Architectures, using web services to communicate between applications. The EJB 2.1 specification will require that all J2EE application servers provide the ability to expose Stateless Session Beans as web services. .NET already relies heavily on web services. This all suggests that Macromedia released Flash Remoting as an intermediate step toward allowing Flash to communicate via web services. Developers should heed this trend toward Service-Oriented Architectures and use Flash Remoting to support a Service-Oriented Architecture that can easily be moved to web services in their own applications.
