Deployment artifacts generated by FX SDK Ant tasks refer to FX version 2.0+ what may not be sufficient if functionality from 2.1 or 2.2 is used. This has been reported in NetBeans bugzilla as:
http://netbeans.org/bugzilla/show_bug.cgi?id=212399

I have verified that FX SDK 2.2 b08 still produces jnlp and html files containing the following 2.0+ references:

  <resources>
    <jfx:javafx-runtime version="2.0+" href="http://javadl.sun.com/webapps/download/GetFile/javafx-latest/windows-i586/javafx2.jnlp"/>
  </resources>

  <applet-desc width="800" height="600" main-class="com.javafx.main.NoJavaFXFallback" name="JavaFXApplication4" >
    <param name="requiredFXVersion" value="2.0+"/>
  </applet-desc>

<script>
    function launchApplication(jnlpfile) {
        dtjava.launch( {
                url : 'JavaFXApplication4.jnlp',
                jnlp_content : 'I deleted this deleted to save space, PS'
            },
            {
                javafx : '2.0+'
            },
            {}
        );
        return false;
    }
</script>

<script>
    function javafxEmbed() {
        dtjava.embed(
            {
                url : 'JavaFXApplication4.jnlp',
                placeholder : 'javafx-app-placeholder',
                width : 800,
                height : 600,
                jnlp_content : 'I deleted this deleted to save space, PS'
            },
            {
                javafx : '2.0+'
            },
            {}
        );
    }
    <!-- Embed FX application into web page once page is loaded -->
    dtjava.addOnloadCallback(javafxEmbed);
</script>

Ideally it would be good to refer the minimum FX RT version on which the particular FX application would be able to run, regardless which FX SDK is used to create it. But such detection would probably be hard and/or unreliable, thus the simpler approach seems more feasible - to refer in the above artifacts to the same FX version that has been used to create the application, i.e., 2.0+ for applications created in FX SDK 2.0.x, 2.1+ for applications created in FX SDK 2.1.x, 2.2+ for applications created in FX SDK 2.2.x, etc.

Remark: this issue is probably related to RT-19524.