StdJDBCDelegate's method selectJobForTrigger setup a JobDetail with this:
JobDetail job = new JobDetail();
job.setName(rs.getString(1));
job.setGroup(rs.getString(2));
job.setDurability(rs.getBoolean(3));
job.setRequestsRecovery(rs.getBoolean(4));

The corresponding Query from StdJDBCConstants:

public static final String SELECT_JOB_FOR_TRIGGER = "SELECT J."
            + COL_JOB_NAME + ", J." + COL_JOB_GROUP + ", J."
            + COL_IS_DURABLE
            + ", J." + COL_IS_STATEFUL + " FROM "
            + TABLE_PREFIX_SUBST
            + TABLE_TRIGGERS + " T, " + TABLE_PREFIX_SUBST
            + TABLE_JOB_DETAILS
            + " J WHERE T." + COL_TRIGGER_NAME + " = ? AND T."
            + COL_TRIGGER_GROUP + " = ? AND T." + COL_JOB_NAME + " = J."
            + COL_JOB_NAME + " AND T." + COL_JOB_GROUP + " = J."
            + COL_JOB_GROUP;

Is seems, the Column IS_STATEFUL is fetched into the RequestsRecovery Field of JobDetail. This seems to be a Bug or a dirty Hack.