Do I add read committed after SET TRANSACTION ISOLATION LEVEL SERIALIZABLE? Inside a stored procedure, I have the following : ( sql server 2008 )

 SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
 BEGIN TRANSACTION getStuff
 BEGIN TRY 
    /*  some selects, updates, etc, etc. */
    ....
    COMMIT TRANSACTION getStuff
 END TRY
 BEGIN CATCH 
   ...
 END CATCH


Since this is transaction based, my thought was the rest of the database connections will not be affected by the SERIALIZABLE. 

Do I need to implicitly set isolation level to read committed after my commit? Will this adversely effect other connections between my application server and database server?
The command is TRANSACTION ISOLATION LEVEL, not SERVER ISOLATION LEVEL. It only changes the isolation level for the transaction scope.