No, there is more to it than just removing a reference. What some do is to code using early bound methods but make the production version late bound.
See the links here if you want to learn more. http://lmgtfy.com/?q=vba+late+binding+vs+early+binding
Here is a quick example where I show how to use the Scripting.FileSystemObject early bound method method and the late bound method is commented out.
Sub CopyFileToDir(filespec, Destination)
'Late bound
'dim fs as Object
'Set fs = CreateObject("Scripting.FileSystemObject")
'Early bound
'Needs Reference: MicroSoft Script Runtime, scrrun.dll
'Instructions: http://support.microsoft.com/default.aspx?scid=kb;en-us;186118
Dim fs As Scripting.FileSystemObject
Set fs = New FileSystemObject
fs.CopyFolder ThisWorkbook.path, "t:\", True
fs.CopyFile filespec, Destination
End Sub